Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0477

reference: 231-tree-1
name: 0477
tree-preservation-order: undefined
231-tpo-1
uprn
address-text
point: POINT (-1.002143 50.850021)
geometry: MULTIPOLYGON (((-1.002100 50.850016,-1.002102 50.850024,-1.002108 50.850032,-1.002117 50.850038,-1.002129 50.850042,-1.002142 50.850043,-1.002155 50.850042,-1.002177 50.850033,-1.002183 50.850025,-1.002185 50.850017,-1.002183 50.850008,-1.002177 50.850001,-1.002168 50.849995,-1.002156 50.849991,-1.002143 50.849989,-1.002118 50.849994,-1.002109 50.850000,-1.002102 50.850008,-1.002100 50.850016)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL